deps: Update all bundler plugin instances to latest & allow caret ranges #16641
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a version is released with a buggy bundler plugin dependency pinned, it can lead to problems. IMHO it should be fine to allow
^
ranges there to ensure bugfixes etc. are pulled in? Or is there a good reason not to do that here? API should be stable in this regard.Note: Astro& solidstart remain on
@sentry/vite-plugin
v2.x as that has more stuff exposed, did not want to get into that right now... something for v10?@sentry/vite-plugin
to v3 for astro SDK #16643@sentry/vite-plugin
to v3 for solidstart SDK #16642